Jack’s book is really about maximizing outcomes generated by engineering。 He answers not an easy question about where we are in the value chain and how we， software leaders， can measure the effectiveness of our organization。 The book connects the three amigos' rules of product engineering， a simple but powerful concept of setting organizational structure based on Jack’s theory of Technical Coherence， and finally， how to fund all of that。 I think that fans of Team Topologies will find it useful a Jack’s book is really about maximizing outcomes generated by engineering。 He answers not an easy question about where we are in the value chain and how we， software leaders， can measure the effectiveness of our organization。 The book connects the three amigos' rules of product engineering， a simple but powerful concept of setting organizational structure based on Jack’s theory of Technical Coherence， and finally， how to fund all of that。 I think that fans of Team Topologies will find it useful as well。 The chapter about financing technical debt is an important one – it gives a good overview of what this debt is （and what it is not） and gives practical advice on what to do with it。 The last part of the book is a bit hand-wavy。 Especially the communication design part feels like a pick of the iceberg。 。。。more